Click any tag below to further narrow down your results
Links
Perplexity's new Context API lets AI agents pull up to 10 web pages at once and get back clean Markdown, HTML, links, and query-matched passages instead of raw HTML full of ads and navigation. Developers can control how fresh the content must be, from cached copies to live fetches.
- Returns clean Markdown with boilerplate like cookie banners, navigation, and ads stripped out, and can return only passages relevant to a query, so the model processes less text.
- Freshness is adjustable: by default it uses a cached copy from the last two days, but max_age_seconds set to 0 forces a live read, and cache_only prevents live requests entirely.
- In Perplexity's own evaluation, 92.3% of URLs returned usable content, 87.9% of key facts were recovered, and content precision was 80.3%.
Unblocked argues that giving an agent access to Slack, Jira, and GitHub through separate connectors isn't enough, because the agent still has to search each silo, reconcile conflicting answers, and guess at unwritten team conventions. Its benchmarks claim up to 83% faster task completion and about 40% fewer tokens with a context engine doing that work upfront.
- Per-source connectors return documents from one system, so cross-source questions like "why does the payment service retry like this?" force the agent to assemble answers itself at inference-time token cost.
- Connectors can't tell which source is current when a Confluence page, a later Slack thread, and a PR comment disagree; the article says a context engine resolves contradictions with recency and authority signals before answering.
- Unwritten conventions and expertise patterns exist only across systems over time, so no query can retrieve them. The article's benchmarks show a 9.5/10 convention-following score with context versus 2/10 without.
- Each direct connector adds its own credential and permission model, which the article presents as a security burden that a single server-side connection reduces.